Purpose

This pull request introduces enhanced support for OpenID Connect (OIDC) discovery and endpoint configuration across the JavaScript and React SDKs. The changes allow developers to customize OIDC endpoint resolution, support platform-specific defaults, and expose OIDC discovery data through React context. This improves flexibility for different deployment scenarios and makes it easier for applications to work with non-standard or custom OIDC providers.

OIDC Discovery and Endpoint Configuration Enhancements:

• Added support for a discovery config object and endpoints overrides in the main Config interface, allowing granular control over how OIDC endpoints are resolved, including the ability to disable or customize well-known discovery and override individual endpoint URLs.
• Introduced platform-specific logic in the legacy client to use new OIDC discovery constants and automatically set the well-known endpoint for Asgardeo V2 platforms if not provided. [1] [2] [3] [4] [5] [6]
• Exported the OIDCDiscoveryApiResponse type for use in both JavaScript and React packages. [1] [2] [3]

SDK API and Context Improvements:

• Added a new getDiscoveryResponse() method to both the JavaScript and React clients, enabling consumers to fetch the latest OIDC discovery document data. [1] [2] [3]
• Updated the React context (AsgardeoContextProps) and provider to include a discovery property, exposing the well-known OIDC discovery response to all context consumers. [1] [2] [3] [4] [5] [6] [7] [8]

These changes make the SDKs more adaptable to various OIDC deployments, improve developer ergonomics, and provide better visibility into OIDC provider metadata for advanced use cases.

Related Issues

• Fixes Expose OIDC discovery response from useAsgardeo hook asgardeo#4

Related PRs

• N/A

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?